Systems and methods for mobile device-based item acquisition and tracking

ABSTRACT

Systems, methods, and computer-readable media are provided for enabling mobile device-based item acquisition and tracking. One exemplary method performed on a mobile device comprises entering a wireless scan mode, detecting a signal from a tag associated with an item in a first area and in proximity to the tag, presenting information associated with the tag, and adding the information to a list. The method further comprises detecting a second tag in a second area, and sending the list to a second device. A second exemplary method performed by a processing terminal comprises receiving the list from a mobile device, entering a wireless scan mode, detecting a signal from a tag associated with an item in proximity to the tag, determining whether the item associated with the detected tag is present on the received list, and enabling the mobile device to complete a transaction to purchase the item. User interfaces are also provided for presenting information related to the above methods and receiving inputs from users to accomplish one or more related methods.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/182,126, filed Jun. 19, 2015, the disclosure of which isincorporated entirely herein by reference.

BACKGROUND

Reliably determining a set of items that are being transported from oneplace to another is a problem that exists in multiple fields anddisciplines.

As one example, a consumer at a brick-and-mortar store location mayplace upwards of 30 items into a single shopping cart. When the consumerreaches a point of sale device, such as a cash register or aself-checkout device, the consumer must unload all of the items from thecart, place them on a sticky and/or germ-covered conveyor belt, manuallyscan each item or select each item from a menu. After paying for theitems, the consumer or a clerk must place each item into a new bag andrepack the shopping cart. When the consumer wants to buy a large item,they will typically need to find a sales clerk because the item cannoteasily be transported to the point of sale or scanned. Finally, such ashopping experience can lead to errors, such as the clerk accidentallyscanning an item twice or not scanning an item at all, that can lead tothe consumer being charged too much or the store location giving away anitem without payment.

As another example, a construction company may store goods such aslumber, nails, cement mix, or backhoes in warehouses. When moving to anew job site, the building company may need to transfer these goods tothe new job site. Typical systems involve marking each item or containerwith a serial number, writing down each serial number, placing eachserial number on a list, and shipping the goods with the list. When thegoods arrive at the job site, a foreperson or inventory specialist mayneed to check the list to ensure that all goods were received. Thiscauses delays and extra costs because a human being must manuallydetermine whether goods were misplaced, modified, or stolen.

Moreover, while some computerized solutions exist for tracking items,they typically rely on large equipment that manually scans each item andrequires confirmation from a user before taking any action with thoseitems (such as purchase or movement of the items). This is inconvenient.Moreover, such systems typically require specialized equipment that isexpensive, require manual entry of information about the items, cannotdetermine when a user has decided to not keep an item, cannot performfunctions or initiate transactions for the user, and do not provide theinteractivity necessary to ensure that a user fully understands when anitem is ready to be purchased or checked out.

There is thus a need to address these and other issues. The presentdisclosure provides devices, methods, systems, and computer-readablemedia to solve these and other issues.

SUMMARY

Disclosed embodiments include methods, systems, and computer-readablemedia configured to, for example, provide mobile device-based itemacquisition and tracking. In one aspect, an exemplary method isprovided. The method, which may be performed on a mobile device,comprises entering a wireless scan mode, detecting a signal from a tagassociated with an item in a first area and in proximity to the tag,presenting information associated with the tag, and adding theinformation to a list. The method further comprises detecting a secondtag in a second area, and sending the list to a second device, such as aprocessing terminal (e.g., a checkout device).

A second exemplary method, which may be performed by a processingterminal such as a checkout device, comprises receiving a list from amobile device, entering a wireless scan mode, detecting a signal from atag associated with an item in proximity to the tag, determining whetherthe item associated with the detected tag is present on the receivedlist, and enabling the mobile device to complete a transaction topurchase the item.

User interface methods are also provided for presenting informationrelated to the above methods and receiving inputs from users toaccomplish one or more related methods. For example, a third exemplarymethod, which may be performed by a mobile device, comprises detecting asignal from a tag associated with an item in a first area and inproximity to the tag, and presenting a user interface on the mobiledevice including: first item information associated with the tag, seconditem information associated with a second tag that is within scanningrange of the mobile device, and buttons configured to cause items to nolonger be displayed on the user interface. The method further comprisesdetecting a third tag associated with a second area separate from thefirst area, presenting at least one of the first item information andsecond item information and a request to confirm checkout, receiving aconfirmation from the user, and based on receiving a confirmation,sending a message over a wireless network to initiate checkout.

Systems and computer-readable media implementing the above method arealso provided.

Aspects of the disclosed embodiments may include tangiblecomputer-readable media that stores software instructions that, whenexecuted by one or more processors, are configured to and capable ofperforming and executing one or more of the methods, operations, and thelike consistent with the disclosed embodiments. Also, aspects of thedisclosed embodiments may be performed by one or more processorsconfigured as special-purpose processor(s) based on softwareinstructions that are programmed with logic and instructions thatperform, when executed, one or more operations consistent with thedisclosed embodiments. Moreover, aspects of the disclosed embodimentsmay be implemented on specialized (rather than generic) equipment ordevices.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system, consistent withdisclosed embodiments.

FIG. 2 is a diagram of an exemplary electronic system, consistent withdisclosed embodiments.

FIG. 3A is a diagram of an exemplary item that can be moved by aconsumer and a corresponding tag.

FIG. 3B is a diagram of an exemplary item that may not be able to bemoved by a consumer and a corresponding tag.

FIG. 4A is a flowchart of an exemplary process for discovering itemsassociated with tags using a mobile device.

FIG. 4B is a flowchart of an exemplary process for determining whether amobile device is still within range of a previously-detected item.

FIG. 4C is a flowchart of an exemplary process for enabling checkout ofitems discovered using a mobile device.

FIG. 5A is a diagram of an exemplary user interface for a mobile device,providing information on goods in a list associated with the mobiledevice and goods near the mobile device.

FIG. 5B is a diagram of an exemplary user interface for a mobile device,requesting confirmation that an item is no longer desired.

FIG. 5C is a diagram of an exemplary user interface for a mobile device,providing a list of items in a shopping cart before checkout.

FIG. 5D is a diagram of an exemplary user interface for a mobile device,providing a final receipt related to purchased items.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts. Embodiments of the presentdisclosure relate to a mobile device detecting tags affixed to orassociated with items and maintaining a list of those detected items onthe mobile device or another device. In some embodiments, the list maybe a shopping cart or checkout list.

FIG. 1 is a block diagram of an exemplary system 100 for performing oneor more operations consistent with the disclosed embodiments. In oneembodiment, system 100 may include one or more of the following: anetwork 101, a financial services provider (FSP) 103, a merchant device105, a database 107, a point-of-sale (POS) device 109, a checkout tag111, a mobile device 113, small item tags 116A, 1168, 116C, and 116D,and large item tag 116E. The components and arrangement of thecomponents included in system 100 may vary. Thus, system 100 may includeother components that perform or assist in the performance of one ormore processes consistent with the disclosed embodiments.

Components of system 100 may be computing systems configured to providesystems and method for pre-authorizing a transaction request, consistentwith disclosed embodiments. As further described herein, components ofsystem 100 may include one or more computing devices (e.g., computer(s),server(s), etc.), memory storing data and/or software instructions(e.g., database(s), memory devices, etc.), and other known computingcomponents. In some embodiments, the one or more computing devices maybe configured to execute software instructions stored on one or morememory devices to perform one or more operations consistent with thedisclosed embodiments. Components of system 100 may be configured tocommunicate with one or more other components of system 100, includingsystems associated with financial service provider 103, merchant device105, database 107, POS device 109 (also referred to more generallyherein as a processing terminal), and/or mobile device 113. In certainaspects, users may operate one or more components of system 100 toinitiate and provide input for one or more operations consistent withthe disclosed embodiments.

Network 101 may be any type of network configured to providecommunications between components of system 100. For example, network101 may be any type of network (including infrastructure) that providescommunications, exchanges information, and/or facilitates the exchangeof information, such as the Internet, a Local Area Network, Near-FieldCommunication (NFC), Bluetooth, or other suitable connection(s) thatenables the sending and receiving of information between the componentsof system 100. In other embodiments, one or more components of system100 may communicate directly through a dedicated communication link(s),such as links between financial service provider 103, merchant device105, POS device 109, and/or mobile device 113.

Financial service provider 103 may be an entity that provides,maintains, manages, or otherwise offers financial services. For example,financial service provider 103 may be a bank, credit union, credit cardissuer, or any other type of financial service entity that generates,provides, manages, and/or maintains financial service accounts for oneor more users. Financial service accounts may include, for example,credit card accounts, loan accounts, checking accounts, savingsaccounts, reward or loyalty program accounts, and/or any other type offinancial service account known to those skilled in the art. Financialservice provider system 103 may include infrastructure and componentsthat are configured to generate and/or provide financial serviceaccounts such as credit card accounts, checking accounts, debit cardaccounts, loyalty or reward programs, lines of credit, or the like.Consistent with certain disclosed embodiments, financial serviceprovider 103 may provide manufacturer-based financial service accounts,which may be financial service accounts that are associated with amanufacturer of products or services, such as a merchant.

Financial service provider 103 may include one or more financial serviceprovider systems (FSP System) 103A. In one aspect, financial serviceprovider system 103A may be one or more computing devices configured toperform one or more operations consistent with disclosed embodiments. Inone aspect, financial service provider system 103A may be a desktopcomputer, a server, or any other type of computing device. Financialservice provider system 103A may include one or more processorsconfigured to execute software instructions stored in memory. The one ormore processors may be configured to execute software instructions thatwhen executed by a processor performs known Internet-relatedcommunication and financial service-based processes. For instance,financial service provider system 103A may execute software thatprovides data used for generating and displaying interfaces, includingcontent on a display device included in, or connected to, mobile device113. Financial service provider system 103A may also receive transactionauthentication requests from mobile device 113, POS device 109, merchant105, and/or network 101, and may send these transaction requests toauthorization system 103B for processing. Financial service providersystem 103A may also send responses to the received transaction requeststo mobile device 113, merchant 105, POS device 109, and/or network 101.

Financial service provider 110 may include one or more authorizationsystems 103B. In one aspect, authorization system 103B may be one ormore computing devices configured to perform one or more operationsconsistent with disclosed embodiments. For example, authorization system103B may be a desktop computer, a server, or any other type of computingdevice. Authorization system 103B may include one or more processorsconfigured to execute software instructions stored in memory. The one ormore processors may be configured to execute software instructions thatwhen executed by the one or more processors perform methods that enablethe processing of financial transaction authorization requests. Forinstance, processing financial transaction authorization requests mayinvolve communicating with one or more other systems to determinewhether an account associated with the request includes a enough balanceor credit to fulfill the associated transaction. The one or moreprocessors may also be configured to enable the detection of potentiallyfraudulent transaction requests. For instance, authorization system 103Bmay receive a transaction request from financial service provider system103A and may determine whether the received transaction request ispotentially fraudulent, using transaction analysis procedures known inthe art.

Merchant device 105 may be operated by an entity that offers goods,services, and/or information, such as a big box retailer (e.g., asuperstore/supercenter), a specialty store (e.g., a running store), agrocery store, a service provider (e.g., a utility company), or anyother type of entity that offers goods, services, and/or informationthat consumers (such as end-users or other business entities) maypurchase, consume, use, etc.

Merchant device 105 may include one or more computing systems, such asserver(s), desktop computers, etc., that are configured to executestored software instructions to perform operations associated with amerchant, including one or more processes associated with processingpurchase transaction requests, generating transaction request data,generating product data (e.g., SKU data) relating to transactionrequests, etc. Merchant device 105 may perform one or more operationsconsistent with the disclosed embodiments. For example, merchant system105 may receive information related to a list of items displayed and/orstored on mobile device 113 (e.g., a shopping cart). Merchant device 105may also store the list of items in database 107 and/or memory inmerchant device 105. Merchant device 105 may also receive identifiersassociated with tags 116A-116E, perform a lookup in database 107 usingthe identifiers, and send (e.g., to mobile device 113 or POS device 109)information about the associated items, such as price, name, ordescription. The disclosed embodiments are not limited to any particularconfiguration of merchant system 122.

Database 107, in some embodiments, may store information usable bydevices such as merchant device 105, POS device 109, or mobile device113. As one example, database 107 may store information related to tags(e.g., tags 116A-116E) that are placed on items (e.g., items 115A-115E).The information may include, for example, one or more unique identifiersthat identify an item that a tag is attached to. Examples would includea 16-bit UUID (or a “Universally Unique Identifier”), a two-bit majoridentifier, a two-bit minor identifier, etc. Database 107 may, in someembodiments, store information about one or more of these fields, alongwith information related to a product that each tag is attached to orassociated with. For example, if a tag is attached to a cereal box,database 107 may store information about the cereal, such as the name,the weight, the price, the size/weight of the box, nutritioninformation, a UPC (Universal Product Code) on the box, or the like.

As another example, database 107 may include information aboutcustomers. For example, in situations where a user registers mobiledevice 113 in advance of coming to a store, database 107 may storeinformation such as a name of the user, a home address of the user(e.g., for delivery of large items), one or more credit cards, debitcards, checking accounts, or payment accounts (e.g., a PAYPAL username),a phone number, or a description/color image of the user (e.g., forverifying the user's appearance).

POS device 109 may, in some embodiments, be implemented as a cashregister or other device for presenting purchase information to a user,such as a consumer. For example, POS device 109 may be implemented as aself-checkout terminal that presents a list of all goods a customer hasbrought to the vicinity of POS device 109, along with a final total forall of the goods (e.g., including tax and delivery fees). (In someembodiments, for example, where system 100 is not related to a purchasetransaction, POS device 109 may be optional or omitted.)

In some embodiments, merchant device 105 may be combined with database107 and/or POS device 109.

Checkout tag 111 may, in some embodiments, be implemented as one or moretags that indicate to devices (such as mobile device 113) of theboundaries of a particular zone 112 of a physical area such as a store.For example, in situations where system 100 is implemented in a store(e.g., a brick-and-mortar merchant location), checkout tags 111 mayindicate a checkout zone 112. Checkout zone 112, in some embodiments,may be an area surrounding POS device 109 in which a user can use mobiledevice 113 to finalize a current list of goods for purchase. In othersituations (e.g., equipment tracking), checkout tag 111 may indicate anarea in which goods surrounding mobile device 113 should be checked(e.g., using a device to scan for tags associated with such goods) todetermine whether they are in the zone or not.

Mobile device 113 may be one or more computing devices configured toperform one or more operations consistent with disclosed embodiments. inone example, mobile device 113 may be a tablet, a smart phone, acellular phone, a personal digital assistant (PDA), a media device (suchas an iPod®), or any other type of computing device. As mentionedherein, however, the disclosed embodiments are not limited to suchexamples. (For example, in embodiments where a user is not likely tocarry mobile device 113 or mobile device 113 is generally stationary,mobile device 113 may be implemented as a desktop, a laptop, or thelike.)

Mobile device 113 may include one or more processors configured toexecute software instructions stored in memory, such as memory includedin mobile device 113. Mobile device 113 may include software that whenexecuted by a processor performs known Internet-related communication,content display processes, and financial service-related processes for auser of mobile device 113. For instance, mobile device 113 may executebrowser or related mobile display software that generates and displaysinterfaces including content on a display device included in, or incommunication with, mobile device 113. Mobile device 113 may executeapplications and/or communication software that allows mobile device 113to communicate with components over network 101, and generates anddisplays content in interfaces via a display device included in mobiledevice 113. The disclosed embodiments are not limited to any particularconfiguration of mobile device 113. In some embodiments, mobile device113 may be configured to execute software instructions relating tolocation services, such as determining a location using GPS orWi-Fi®networks. For example, mobile device 113 may be configured todetermine a geographic location of mobile device 113 and providecorresponding location and time stamp data.

Mobile device 113 may be configured to communicate with network 101using wired connections (e.g., Ethernet-based connections) or wirelessconnections (e.g., IEEE 802.11 wireless or “Wi-Fi” connections), and maybe configured to communicate with tags 111 and 116A-116E using wirelessconnections (e.g., Bluetooth or Wi-Fi).

Mobile device 113 may be configured to communicate with tags 111 and116A-116E if the tags are inside of a detection zone 114. In someembodiments, mobile device 113 may be set to a particular mode such thatit will only detect tags within detection zone 114. As one example,mobile device 113 may be programmable to detect tags in three differentranges. If tags 111 and 116A-116E are implemented as BLE (Bluetooth LowEnergy tags), there may be three ranges for use by mobile device 113 andtags 111 and 116A-116E: an “immediate” range (within roughly a fewcentimeters of mobile device 113), a “near” range (within roughly 5meters of mobile device 113), and a “far” range (within roughly tenmeters from mobile device 113). These ranges are approximate and maydepend, in part, on the conditions in which the detection takes place.For example, if there is a lot of electromagnetic noise or interferencefrom other tags in the same area, these distances may be reduced.Similarly, repeaters may exist to receive and retransmit signals, whichmay increase these distances. Detection zone 114 may differ based onwhat mobile device 113 is configured to detect (e.g., by the user or bysoftware on mobile device 113).

Product tags 116A-116E, in some embodiments, may be attached to orotherwise associated with items such as 115A-115E, respectively. Eachproduct tag, as explained above with respect to database 107, mayinclude a unique identifier and/or other information identifying an itemto which a tag is attached. In some embodiments, tags 116A-116E may beimplemented as Bluetooth Low Energy (BLE) tags. Tags 116A-116E may alsoinclude sensors such as temperature sensors, weight sensors, motionsensors, accelerometers, or the like.

In exemplary FIG. 1, items 115A, 115B, and 115C are all in a shoppingcart 119 associated with a user holding mobile device 113. Tags 116A,116B, and 116C may include respective information about each item, suchas a unique identifier for the associated tag, a price of the item, adescription of the item, or the like.

Tag 116D (affixed to good 115D) is outside of detection zone 114. Whenmobile device 113 attempts to read data from tags inside of detectionzone 114, mobile device 113 may not receive any data from tag 116D as itis outside of detection zone 114. As another example, if a userinitially possessed item 115D (e.g., in cart 119) but placed it back ona shelf or left it with a store clerk, mobile device 113 may no longerdetect item 115D, and may then determine that the consumer no longerdesires to acquire that item, and may prompt the user to confirm thatitem 115D is no longer desired and/or remove it from a list.

Tag 116E (affixed to heavy item 115E) is also outside of detection zone114. Tag 116E, however, may include data that indicates that heavy item115E is not easily moved, requires store clerk assistance to purchase,and/or is intended to be shipped to a consumer's home. In each of thesesituations, item 115E need not always be within detection zone 114 inorder for a consumer to purchase it. As explained below, in someembodiments, a consumer may confirm a desire to purchase good 115E butmay not need to keep the good inside of detection zone 114 in order tomaintain it on a list or electronic shopping cart maintained on mobiledevice 113. (In other embodiments, item 115E may not be “heavy,” but maybe an item otherwise not suitable to be carried by a user or placed in acart/basket, such as a magazine subscription or digital good.)

In one example embodiment, tags 111 and 116A-116E may also beimplemented using Near-Field Communication (NFC) technology. In anotherembodiment, tags 111 and 116A-116E may be implemented using BLE(Bluetooth Low Energy) devices implementing the Apple iBeacon standard.Other embodiments using other types of tags or sensors are possible aswell (such as Bluetooth, RFID, or the like).

It is to be understood that the configuration and boundaries of thefunctional building blocks of system 100 have been defined herein forthe convenience of the description. Alternative boundaries can bedefined so long as the specified functions and relationships thereof areappropriately performed. Alternatives (including equivalents,extensions, variations, deviations, etc., of those described herein)will be apparent to persons skilled in the relevant art(s) based on theteachings contained herein. For example, financial service providersystem 103 and merchant device 105 may constitute a part of componentsof system 100 other than those specifically described, or may constitutea part of multiple components of system 100 (i.e., a distributedsystem).

FIG. 2 shows an exemplary electronic system 200 consistent withdisclosed embodiments. Variations of exemplary system 200 may be used toimplement portions or all of devices of system 100, such as financialservice provider 103, merchant device 105, database 107, POS device 109,and/or mobile device 113. In one embodiment, system 200 may comprise oneor more processors 221, one or more input/output (I/O) devices 222, andone or more memories 223. In some embodiments, system 200 may take theform of a server, general purpose computer, mainframe computer, or thelike. In some embodiments, system 200 may take the form of a mobilecomputing device such as a smartphone, tablet, laptop computer, or thelike. Alternatively, system 200 may be configured as a particularapparatus, embedded system, dedicated circuit, or the like, based on thestorage, execution, and/or implementation of the software instructionsthat perform one or more operations consistent with the disclosedembodiments.

Processor(s) 221 may include one or more known processing devices, suchas mobile device microprocessors, desktop microprocessors, servermicroprocessors, or the like. The disclosed embodiments are not limitedto a particular type of processor.

Memory 223 may include one or more storage devices configured to storeinstructions usable by processor 221 to perform functions related to thedisclosed embodiments. For example, memory 223 may be configured withone or more software instructions, such as program(s) 224 that performone or more operations when executed by processor 221. The disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory 223 may include a singleprogram or multiple programs that perform the functions of mobile device130. Memory 223 may also store data 225 that is used by one or moreprograms 224.

In certain embodiments, memory 223 may store software executable byprocessor(s) 221 to perform one or more methods, such as the methodsrepresented by the flowcharts depicted in FIGS. 4A-4C and/or the methodsassociated with user interfaces in FIGS. 5A-5D.

I/O devices 222 may be one or more devices configured to allow data tobe received and/or transmitted by system 200. I/O devices 222 mayinclude one or more digital and/or analog devices that allow system 200to communicate with other machines and devices, such as other componentsof system 100. For example, I/O devices 222 may include a screen fordisplaying messages to a user (such as a consumer). I/O devices 222 mayalso include one or more digital and/or analog devices that allow a userto interact with system 200 such as a touch-sensitive area, keyboard,buttons, or microphones. I/O devices 222 may also include othercomponents known in the art for interacting with a user. I/O devices 222may also include one or more hardware/software components forcommunicating with other components of system 100. For example, I/Odevices 222 may include a wired network adapter, a wireless networkadapter, a cellular network adapter, or the like. Such networkcomponents enable system 200 to communicate with other systems to sendand receive data.

The components of system 200 may be implemented in hardware, software,or a combination of both hardware and software, as will be apparent tothose skilled in the art. For example, although one or more componentsof system 200 may be implemented as computer processing instructions,all or a portion of the functionality of system 200 may be implementedinstead in dedicated electronics hardware.

FIG. 3A is a diagram of an exemplary item 301 that can be moved by auser and a corresponding tag 302. Item 301 may be a small item that fitsinside of a shopping cart, a shopping basket, or a user's arms. Forexample, item 301 is depicted as a cereal box. Item 301 is associatedwith tag 302. In some embodiments, for an item that can be easilytransported by a user, such as a cereal box, tags are attached to theoutside or the inside of the item to enable easy capture of the tag by adevice (such as POS device 109 or mobile device 113). As explainedabove, tag 302 may contain a unique identifier or other informationabout item 301, such as a price, a name, a weight, or the like.

When a consumer holding or using mobile device 113 picks up cereal box301, cereal box 301 may enter the scanning range of mobile device 113.Mobile device 113 may read tag 302, may determine that tag 302 isrelated to an item that can be carried by the user, and may place item302 onto a list associated with mobile device 113 (e.g., an electronicshopping cart).

FIG. 3B is a diagram of an exemplary item 304 that may not be readilymovable (e.g., suitable for being carried, set in a shopping cart, etc.)by a consumer and a corresponding tag 305. Promotional area 303 includesa television 304 and a tag 305. A consumer may be unable to readilycarry television 304 because the consumer does not have a cart largeenough to carry it, because it is too heavy, because the defaultdelivery option for television 304 is shipment to the consumer's home,etc. In these embodiments, tag 305 may not be affixed to or otherwiseattached to item 304 because the consumer will not carry item 304 to aPOS device 109 or checkout zone 112. Rather, a consumer holding or usingmobile device 113 may stand in the vicinity of tag 305. Tag 305 mayinclude information that indicates to mobile device 113 that item 304 istoo large to be carried by the consumer.

When a consumer holding or using mobile device 113 stands near tag 305,mobile device 113 may read tag 305, may determine that tag 305 isrelated to an item (television 304) that cannot be carried by the user,may prompt the user to learn more about television 304, add television304 to a list associated with mobile device 113 (e.g., an electronicshopping cart), ship television 304 to a particular address, requestthat a store clerk bring television 304 to an area for later pickup,etc.

FIG. 4A is a flowchart of an exemplary process for discovering itemsassociated with tags 400 using a mobile device 113. The process beginswith step 401, where mobile device 113 enters a scan mode. As explainedabove, mobile device 113 may scan for tags in a particular zonesurrounding mobile device 113. For example, step 401 may representmobile device 113 scanning for tags in “near” mode (finding, forexample, tags that are within five meters of mobile device 113).

Tag 400 may also begin transmitting data in step 402. In someembodiments, for example, embodiments where tag 400 is implemented as aBluetooth Low Energy tag, tag 400 may transmit data at the end of a timeinterval (e.g., such as every 500 ms). So, in embodiments where tag 400is a powered tag, step 402 may represent a periodic sending of data bytag 400. In other embodiments, such as those where passive RFID or othernon-powered tags are used, tag 400 may only transmit data when itreceives ambient energy transmitted by mobile device 113 (e.g., emittinga signal after receiving energy from radio waves generated by mobiledevice 113). Thus, in embodiments where tag 400 is a non-powered tag,step 402 may represent tag 400 receiving electromagnetic energy frommobile device 113 and using that energy to transmit data stored in tag400.

In step 403, mobile device 113 may receive the data advertised by tag400 and may determine what the data represents. For example, mobiledevice 113 may receive one or more identifiers (unique or non-unique)stored on tag 400. Step 403 may also represent mobile device 113 sendingone or more of these identifiers to a device (e.g., sending to merchantdevice 105 via network 101) to request information about tag 400 or theitem that tag 400 is associated with. For example, mobile device 113 mayreceive a 128-bit UUID such as ‘a326e1d9-ed1c-427f-87e9-2d3a46bf6342’from tag 400. Mobile device 113 may also receive a “major” identifiersuch as ‘01’ and a “minor” identifier such as ‘a5.’ (In someembodiments, the major and minor identifiers may be used to identifydifferences between similar items, such as a placement or a localizationof the item.) Mobile device 113 may then send the UUID and the majorand/or minor identifiers to merchant device 105. In step 404, merchantdevice 404 may retrieve one or more records associated with at least oneof the received identifiers (UUID, major, minor, etc.) from a database(such as database 107), and return the information to mobile device 113.(In another embodiment, mobile device 113 may retrieve the records fromdatabase 107 directly.)

In step 405, mobile device 113 may determine whether to add theinformation received from merchant device 105 to a list. This list maybe, for example, a shopping cart or other list stored on mobile device113.

In some embodiments, step 405 may occur automatically. For example,mobile device 113 may be programmed to detect tag 400, determine thattag 400 is associated with an item that is easily carried by a consumer(e.g., a box of cereal), and determines that it should be added to alist on mobile device 113. Similarly, for other items associated with atag 400, mobile device 113 may prompt the consumer to approve the addingof an item to a shopping cart. For example, if a consumer walks throughan aisle of 60-inch televisions, mobile device 113 may present one ormore of the televisions to the consumer requesting that the consumerconfirm the addition to the shopping cart. (This avoids, for example, aconsumer accidentally purchasing ten TVs in the same shopping trip.)

If the consumer does not wish to add the item to the list, or the mobiledevice 113 determines that the item should not be added to the list(e.g., because the tag 400 exited the range of mobile device 113 or theitem is not eligible to be added to the list), the process may return tostep 403 to read data from any other tags in the vicinity of mobiledevice 113. If, however, mobile device 113 determines to add the item tothe list, the process continues to step 407.

In step 407, mobile device 113 determines whether or not to ship theitem associated with tag 400. For example, if the consumer hasapproached a large item that cannot readily be carried in a shoppingcart either because of size or logistics (e.g., a three-person kayak, avacation package, a magazine subscription, etc.), mobile device 113 mayprompt the user to accept shipment of the item, for example, to a homeaddress of the consumer stored in database 107. If the consumer wishesthe item brought to the front of the store, mobile device 113 may send amessage indicating this to merchant device. The process may thencontinue to step 408, where merchant device 105 may initiate shipment ofthe item. This includes, for example, notifying a store clerk (e.g., bysending a message to a wireless device held by the clerk) to obtain theitem from a storeroom, find a box large enough to ship the item,determine pricing for the item, determine shipment options, etc. (Thesesteps, as well as others, may also be performed by a computer systemdedicated or partially dedicated to determining shipment details.) Afterinitiating shipping, the process may continue to step 411.

If, however, mobile device 113 does not request that the item be shipped(e.g., because it is not eligible for shipping or the consumer does notwish to ship the item), the process may continue to step 409. In step409, mobile device 113 determines whether or not the item associatedwith tag 400 is “large.” Defining what is “large” may depend in part onthe environment in which the process takes place. For example, if themobile device and tags are located in a supermarket, items as large as a25-pound turkey (roughly 16×13×8 inches) may qualify as “small” becausea user of mobile device 113—e.g., a shopper—would typically have a metalshopping cart in which they can place goods. As another example, if themobile device and tags are located in a small equipment warehouse whereeach user would have a small, hand-carried basket, items larger than asmall box of nails (roughly 2×3×3.5) may qualify as “large” becauseusers may not be able to carry many items at once. Mobile device 113may, in some embodiments, define what constitutes a “large” item basedon the preferences of the user. In other embodiments, merchant 105and/or data stored on the tag (e.g., tag 116E), may define whether anitem is “large.”

In any case, if the item associated with tag 400 is “large,” or if theuser desires it, the item may be brought to the front of the store forthe user of mobile device 113. For example, if mobile device 113 detectsan item that is too large to place into a cart but small enough to placeinto a vehicle, mobile device 113 may prompt the user of mobile device113 to confirm whether the item should be brought to the front of thestore (e.g., near the POS device 109 and/or inside of zone 112) or to apickup department in the store. If the consumer wishes the item broughtto the front of the store, mobile device 113 may send a messageindicating this. The process may then continue to step 408, wheremerchant device 105 may initiate the movement of the item. Thisincludes, for example, notifying a store clerk (e.g., by sending amessage to a wireless device held by the clerk) to obtain the item froma storeroom or the shelf and bring it to zone 112 or a package pickupdepartment in the store. (These steps, as well as others, may also beperformed by a computer system dedicated or partially dedicated todetermining how to locate and move the item for the user.) The processmay continue to step 411.

In step 411, mobile device 113 may add the item associated with tag 400to the list on mobile device 113. Adding the item to the list may alsocomprise, for example, storing an indication of whether the item isbeing carried or moved by the consumer (e.g., located in a cart, abasket, or carried in the consumer's arms), whether the item is beingmoved (or will be moved) by a store clerk (e.g., to the front of thestore or a package pickup department), or whether the item will beshipped to the consumer's home.

In step 413, mobile device 113 determines whether or not other tags weredetected in the vicinity of mobile device 113. If so, the process maycontinue to step 403, where mobile device 113 may read data from thenext detected tag.

In either case (i.e., whether or not more tags are present), afteradding tag 400 to the list in step 411, the process may continue to FIG.4B. (In some embodiments, the process may continue to FIG. 4B only foritems that are determined to be small enough to be carried by a user orplaced in a cart/basket.)

FIG. 4B is a flowchart of an exemplary process for determining whethermobile device 113 is still within range of a previously-detected item.As explained above, in some embodiments, the process in FIG. 4B may beperformed only with respect to certain items, for example, items smallenough to be carried by a user or placed in a cart/basket.

The process in FIG. 4B, in some embodiments, may begin after adding atag to a list on mobile device 113. For example, each time a tag 400 isdetected and added to the list, the process in FIG. 4B may begin. (Theprocess in FIG. 4B could be, for example, initiated as a separate threadon the processor of mobile device 113, so as to ensure mobile device 113continues detecting other tags or presenting other information to theperson utilizing mobile device 113.)

In step 421, mobile device 113 may initiate a timer for detected tag400. The timer, in some embodiments, may be based on particularproperties of tag 400 and mobile device 113. For example, in embodimentswhere tag 400 is a powered tag, such as one implemented in accordancewith Bluetooth Low Energy (BLE) standards, tag 400 may be programmed toadvertise data on a periodic basis, such as every 500 milliseconds.Mobile device 113 may be configured to initiate the timer to be equal toor more than the expected timing for the advertisement. For example, iftag 400 advertises every 500 ms, mobile device may initiate a timer thatfires at intervals such as 550 ms, 600 ms, or 1000 ms.

After the timer expires, mobile device 113 may determine whether tag 400is in the vicinity of mobile device 113. For example, if the timer wasset for 500 ms, mobile device 113 may determine whether it has receiveddata in the form of Bluetooth communications during the preceding 500ms. In step 425, mobile device 113 may determine whether tag 400 isstill in the vicinity of mobile device 113, based on whether data wasreceived from tag 400 during that time period. If so, the process maycontinue to step 421 to reinitiate the timer and listen for the datafrom tag 400 again. If not, mobile device 113 may proceed to step 427.In step 427, mobile device 113 may remove the item associated with tag400 from the list. If mobile device 113 comes back into the vicinity ofthat item, it can be added to the list again, as explained above withrespect to steps 401-411 in FIG. 4A.

FIG. 4C is a flowchart of an exemplary process for enabling checkout ofitems discovered using mobile device 113.

When a user enters a checkout zone 112 (FIG. 1), the user may know thatshe has entered zone 112 because of signage, markings, or the like.Mobile device 113 may determine that it is inside of checkout zone 112because of checkout tag 111. One or more checkout tags 111 may be usedto indicate that the area around tag(s) 111 comprises checkout zone 112.Zone 112 may be used, in some embodiments, to indicate to mobile device113 that the current area is for finalizing transactions. For example,if implemented in a merchant location, checkout zone 112 may represent apayment area, where tags are detected and the price associated with eachitem is tallied for payment. As another example, if implemented in awarehouse, checkout zone 112 may represent a shipment area, where tagsare counted and a shipping bill is printed or transmitted to ensure thatthe items in the area make it to a job site.

In embodiments where tag 400 is a powered tag, step 432 may represent aperiodic sending of data by tag 400, such as once every 500milliseconds. In embodiments where checkout tag 111 is a powered tag,step 434 may represent a periodic sending of data by checkout tag 111,such as once every 250 milliseconds.

In step 431, mobile device 113 may poll for checkout tag 111. Pollingfor checkout tag 111 may comprise, for example, determining whethercheckout tag 111 is broadcasting a signal indicating the existence ofcheckout zone 112. (For example, instead of a UUID or major/minoridentifiers, as transmitted by tag 400, checkout tag 111 may transmitother information indicating the existence of the zone.) In step 433, ifmobile device 113 has detected checkout tag 111, the process may thenproceed to step 435. In step 435, mobile device 113 may finalize thelist on mobile device 113 (e.g., by adding data to the list indicatingthat it is ready for checkout), and may send the list to merchant device105. The list sent to merchant device 105 may include, for example, thename of the items, identifier(s) associated with each tag, the locationof the item (e.g., in a cart/requested to be shipped), or otherinformation.

In step 437, merchant device 105 may receive the list and determine theprice for each item on the list. For example, merchant device 105 mayquery database 107 for each tag identifier received in order todetermine the price for each associated item, add each price together,determine appropriate tax and/or shipping charges, and generate a finalamount for payment. In step 439, merchant device 105 may send the list(along with any determined price) to POS device 109.

In step 441, POS device 109 may receive the list from merchant device105. POS device 109 may also scan checkout zone 112 to determine whichtags, and thus which items, are located in checkout zone 112. In step443, POS device 109 may compare the items determined as being incheckout zone 112 with the items on the list received in step 441. Steps445 and 447 represent POS device 109 modifying the received list. Forexample, if the list received in step 441 includes {“bacon,” “cheddarcheese,” and “hard rolls”}, but the items determined in step 441 includepork roll, eggs, cheddar cheese, and hard rolls, POS device may, in step445, remove bacon from the list and, in step 447, add pork roll and eggsto the list.

In step 449, POS device 109 may generate and display a final list forapproval by the user. (In some embodiments, displaying the final listmay be performed by mobile device 113.) POS device 109 and/or mobiledevice 113 may then prompt the user to approve the list of items. If theuser approves the list, the process continues to step 455 and POS device109 processes the transaction (e.g., by sending a transaction request toFSP 103 in FIG. 1). If the user does not approve the list, the processcontinues to step 453, where the user may utilize mobile device 113 tomodify the list (e.g., by removing items from the list).

In some embodiments, POS device 109 and merchant device 105 may becombined into a single device or may perform different combinations ofthe steps illustrated in FIG. 4C. Additionally, in some embodiments,steps 437-455 may be performed by one or more of mobile device 113,merchant device 105, or POS device 109.

FIG. 5A is a diagram of an exemplary user interface for mobile device113, providing information on goods in a list associated with mobiledevice 113 and goods near mobile device 113.

The user interface in FIG. 5A may include two portions—a portion 500indicating items that are in the vicinity of mobile device 113 (e.g.,detected using the scanning methods explained above) and a portion 508indicating items that are already in a list (e.g., a shopping cart).

Portion 500 includes two sections—one of items that are small enough tofit inside of a cart/basket and/or to be carried by a consumer (e.g., abox of cereal). In exemplary FIG. 5A, each item in the first section(labeled “Cart Items”) is accompanied by two buttons. When a userpresses on button 501A (labeled “ADD”), mobile device 113 may add theassociated item to a shopping cart or list stored on the device. Whenthe user presses on button 503A (labeled “?”) mobile device 113 maypresent information about the item (such as price, name, a picture,location, or the like).

In exemplary FIG. 5A, each item in the second section of portion 500(labeled “Large Items”) is accompanied by three buttons. When a userpresses on button 505A (labeled “FRONT”), mobile device 113 sends acommunication to merchant device 105 or POS device 109 indicating theuser's desire that the item be brought to the front of the store orotherwise prepared for pickup. When a user presses on button 506A(labeled “SHIP”), mobile device 113 sends a communication to merchantdevice 105 or POS device 109 indicating the user's desire that the itembe prepared for shipping to the consumer's home, office, or otherlocation. When the user presses on button 507A (labeled “?”) mobiledevice 113 may present information about the item (such as price, name,weight, shipping costs, size, a picture, or the like).

Portion 508 indicates items that are on a list associated with mobiledevice 113. For example, the items on the list may be in a shopping cart(in the case of a store), a book list (in the case of a library), or arequisition list (in the case of a warehouse). In exemplary FIG. 5A,each item in portion 508 (labeled “Current List”) is accompanied by twobuttons. Button 509A (labeled “CART”) indicates that the associated itemis currently in a shopping cart or list stored on the device. When theuser presses on button 509B (labeled “Θ”) mobile device 113 may removethe item from the list or prompt the user to confirm that she wishes toremove it from the list.

FIG. 5B is a diagram of an exemplary user interface for mobile device113, requesting confirmation that an item is no longer desired. Ifmobile device 113 detects that tag 400 is no longer in the vicinity ofmobile device 113, mobile device 113 may indicate that the tag is nolonger detected and request that the user confirm that the item shouldbe removed from the list of items. If the user presses “Yes,” the itemmay be removed. If, however, the user presses “No,” the item may bemaintained in the shopping cart, but the user may be asked to confirmthat he still has the item in his possession.

FIG. 5C is a diagram of an exemplary user interface for mobile device113, providing a list of items in a shopping cart before checkout. Insome embodiments, mobile device 113 may present the interface in FIG. 5Cwhen the mobile device determines that a checkout tag 112 is in thevicinity of mobile device 113 (e.g., steps 433-435 in FIG. 4C). Thiscould indicate, for example, that the user desires to purchase the itemsand leave the store.

The interface in FIG. 5C may display a finalized list of items 520. Thefinalized list may include, for example, items that are small enough tobe carried or placed in a basket/cart (under “In Cart”), items that mustbe picked up by the user after finishing the transaction (under “PackagePickup Dept.”), and items that will be shipped to the user's home afterfinishing the transaction (under “To Be Shipped”). A user may remove anitem from the final list 520 by using corresponding button 521. If theuser presses button 523, mobile device 113 may initiate processing ofthe transaction (e.g., by authorizing a POS device to initiate a creditcard-based transaction to purchase the items). If the user pressesbutton 525, mobile device 113 may prompt the user to continue shoppingor call a store clerk for assistance.

FIG. 5D is a diagram of an exemplary user interface for mobile device113, providing a final receipt 530 related to purchased items. After auser completes the transaction (e.g., by pressing button 523 in FIG.5C), mobile device 113 may present a short receipt for the transaction,indicating the amount of money charged to a credit card and instructingthe user to proceed to the package pickup department to receive one ormore purchased goods. The user may also press on button 531 to view afull receipt with all items listed.

The foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations of theembodiments will be apparent from consideration of the specification andpractice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure can be implemented as hardwarealone. Furthermore, although aspects of the disclosed embodiments aredescribed as being associated with data stored in memory and othertangible computer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. For example, program sections or program modulescan be designed in or by means of Java, C, C++, assembly language, Perl,PHP, HTML, or other programming languages. One or more of such softwaresections or modules can be integrated into a computer system,computer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

1. A method performed by one or more processors on a mobile device,comprising: entering a wireless scan mode on the mobile device;detecting, with the mobile device using the scan mode, a signal from atag associated with an item in proximity to the tag, the item being in afirst physical area; presenting item information associated with the tagon the mobile device; adding the item information to a list; detecting,with the mobile device using the scan mode, a second tag associated witha second physical area; and sending the list to a second device.
 2. Themethod of claim 1, wherein the scan mode is operable to detect one ormore tags emitting a signal in the 2.4 GHz range at less than 5 meters.3. The method of claim 1, wherein the step of detecting the tagcomprises: receiving the information related to the tag on the mobiledevice; determining whether the tag is associated with a first type ofitem or a second type of item; if the tag is associated with the firsttype of item, adding the information to the list, and if the tag isassociated with the second type of item: presenting a request on themobile device to confirm the addition of the information to the list;and based on receiving a confirmation to add the information to thelist, add the information to the list, and wherein detecting the secondtag further comprises initiating a communication to a third devicerequesting one or more items associated with one or more tags associatedwith the second type of item.
 4. The method of claim 1, furthercomprising: maintaining a timer on the mobile device associated with thetag; measuring, using the timer, a first time interval; determining, atthe end of the first time interval, whether the tag is in range of themobile device; and removing the tag from the list when the tag is notdetected at the end of the first interval.
 5. The method of claim 1,further comprising: receiving, from a second device, a confirmationrequest associated with the total; receiving input at the mobile deviceto confirm the total; and sending a confirmation to the second device toconfirm the total.
 6. The method of claim 1, wherein: the list comprisesinformation about items for purchase, the first area and the second areacomprise a store, and the second area is a checkout area of the store.7-11. (canceled)
 12. A mobile device, comprising: memory storingsoftware instructions; a wireless communication device configured tocommunicate with at least one tag; and at least one processor configuredto execute the software instructions to perform a method comprising:entering a wireless scan mode on the mobile device; detecting, with thewireless communication device using the scan mode, a signal from a tagassociated with an item in proximity to the tag, the item being in afirst physical area; presenting item information associated with the tagon the mobile device; adding the item information to a list; detecting,with the wireless communication device using the scan mode, a second tagassociated with a second physical area; and sending the list to a seconddevice.
 13. The mobile device of claim 12, wherein the scan mode isoperable to detect one or more tags emitting a signal in the 2.4 GHzrange at less than 5 meters.
 14. The mobile device of claim 12, whereinthe step of detecting the tag comprises: receiving the informationrelated to the tag on the mobile device; determining whether the tag isassociated with a first type of item or a second type of item; if thetag is associated with the first type of item, adding the information tothe list, and if the tag is associated with the second type of item:presenting a request on the mobile device to confirm the addition of theinformation to the list; and based on receiving a confirmation to addthe information to the list, add the information to the list, andwherein detecting the second tag further comprises initiating acommunication to a third device requesting one or more items associatedwith one or more tags associated with the second type of item.
 15. Themobile device of claim 12, further comprising: maintaining a timer onthe mobile device associated with the tag; measuring, using the timer, afirst time interval; determining, at the end of the first time interval,whether the tag is in range of the mobile device; and removing the tagfrom the list when the tag is not detected at the end of the firstinterval.
 16. The mobile device of claim 12, further comprising:receiving, from a second device, a confirmation request associated withthe total; receiving input at the mobile device to confirm the total;and sending a confirmation to the second device to confirm the total.17. The mobile device of claim 12, wherein: the list comprisesinformation about items for purchase, the first area and the second areacomprise a store, and the second area is a checkout area of the store.18-22. (canceled)
 23. A system for adding list items on a wirelessdevice, comprising: a processor; and a memory containing instructionsthat, when executed by the processor, cause the system to performoperations comprising: entering a wireless scan mode on the mobiledevice; detecting, with the mobile device using the scan mode, a signalfrom a tag associated with an item in proximity to the tag, the itembeing in a first physical area; presenting item information associatedwith the tag on the mobile device; adding the item information to alist; detecting, with the mobile device using the scan mode, a secondtag associated with a second physical area; and sending the list to asecond device.
 24. The system of claim 23, wherein the scan mode isoperable to detect one or more tags emitting a signal in the 2.4 GHzrange at less than 5 meters.
 25. The system of claim 23, whereindetecting the tag comprises: receiving the information related to thetag on the mobile device; determining whether the tag is associated witha first type of item or a second type of item; if the tag is associatedwith the first type of item, adding the information to the list, and ifthe tag is associated with the second type of item: presenting a requeston the mobile device to confirm the addition of the information to thelist; and based on receiving a confirmation to add the information tothe list, add the information to the list, and wherein detecting thesecond tag further comprises initiating a communication to a thirddevice requesting one or more items associated with one or more tagsassociated with the second type of item.
 26. The system of claim 23,further comprising: maintaining a timer on the mobile device associatedwith the tag; measuring, using the timer, a first time interval;determining, at the end of the first time interval, whether the tag isin range of the mobile device; and removing the tag from the list whenthe tag is not detected at the end of the first interval.
 27. The systemof claim 23, further comprising: receiving, from a second device, aconfirmation request associated with the total; receiving input at themobile device to confirm the total; and sending a confirmation to thesecond device to confirm the total.
 28. The system of claim 23, furthercomprising: receiving, from a second device, a confirmation requestassociated with the total; receiving input at the mobile device, whereinthe input consists of revisions to either add an item to the list orremove an item from the list; and sending the confirmation revision tothe second device.
 29. The system of claim 23, wherein: the listcomprises information about items for purchase, the first area and thesecond area comprise a store, and the second area is a checkout area ofthe store.
 30. The system of claim 29, wherein: the second device is aprocessing terminal associated with the checkout area of the store, andthe second device, after receiving the list from the mobile device,determines a sale price of the item on the list.